Distributed weld monitoring system with job tracking

ABSTRACT

Systems and methods for distributed weld monitoring using jobs and job sessions are described. In some examples, a distributed monitoring system comprises a central monitoring station in communication with a user device and a local monitoring station. A user may use the user device to enter weld monitoring data that is subsequently received by the central monitoring station and stored in a central data repository. The central data repository may associate the weld monitoring data with welding data received from a welding device, as well as with a job session that is, in turn, associated with a job.

CROSS-REFERENCE TO RELATED APPLICATION

The present application claims priority to, and is a continuation of,co-pending U.S. non-provisional patent application Ser. No. 16/872,484,filed May 12, 2020, entitled “DISTRIBUTED WELD MONITORING SYSTEM WITHJOB TRACKING,” which claims the benefit of U.S. provisional patentapplication 62/851,216, filed May 22, 2019, entitled “DISTRIBUTED WELDMONITORING SYSTEM WITH JOB TRACKING,” the contents of both which arehereby incorporated by reference in their entirety.

TECHNICAL FIELD

The present disclosure generally relates to weld monitoring systems and,more particularly, to distributed weld monitoring systems with jobtracking.

BACKGROUND

Weld monitoring systems monitor data pertaining to welding operations.Some weld monitoring systems are narrowly focused on monitoringindividual welds or operators. While this may work for simple and/orrepetitive welding tasks, welding jobs that are more complex and/orunique may be poorly served by such a narrow focus.

Additionally, some welding (e.g., for shipbuilding, railcar fabrication,pipe welding, building/bridge construction, etc.) occurs in largeenvironments with multiple operators. In such environments, weldingequipment may be located at a significant distance from monitoringequipment, requiring operators to travel long distances between thewelding equipment and the monitoring equipment.

Limitations and disadvantages of conventional and traditional approacheswill become apparent to one of skill in the art, through comparison ofsuch systems with the present disclosure as set forth in the remainderof the present application with reference to the drawings.

BRIEF SUMMARY

The present disclosure is directed to distributed weld monitoringsystems with job tracking, substantially as illustrated by and/ordescribed in connection with at least one of the figures, and as setforth more completely in the claims.

These and other advantages, aspects and novel features of the presentdisclosure, as well as details of an illustrated example thereof, willbe more fully understood from the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a welding system in communication with a local monitoringstation, in accordance with aspects of this disclosure.

FIG. 2 shows the local monitoring station of FIG. 1 in communicationwith several welding systems, in accordance with aspects of thisdisclosure.

FIG. 3 shows an example distributed weld monitoring system, inaccordance with aspects of this disclosure.

FIG. 4 shows an example data repository of the example distributed weldmonitoring system of FIG. 3 , with data organized according to jobs andjob sessions, in accordance with aspects of this disclosure.

FIG. 5 is an example custom field setup screen, in accordance withaspects of this disclosure.

FIG. 6 a is a flow diagram illustrating an example user devicemonitoring program of the example distributed weld monitoring system ofFIG. 3 , in accordance with aspects of this disclosure.

FIG. 6 b is an example session list screen, in accordance with aspectsof this disclosure.

FIG. 6 c is a flow diagram illustrating an example start new sessionblock of the user device monitoring program of FIG. 6 a , in accordancewith aspects of this disclosure.

FIG. 6 d is an example new session screen, in accordance with aspects ofthis disclosure.

FIG. 7 a is a flow diagram illustrating an example central monitoringprogram of the example distributed weld monitoring system of FIG. 3 , inaccordance with aspects of this disclosure.

FIG. 7 b is a flow diagram illustrating an example start new sessionblock of the central monitoring program of FIG. 7 a , in accordance withaspects of this disclosure.

FIG. 8 a is a flow diagram illustrating an example local monitoringprogram of the local monitoring station of FIG. 3 , in accordance withaspects of this disclosure.

FIG. 8 b is a flow diagram illustrating an example activity trackingblock of the local monitoring program of FIG. 8 a , in accordance withaspects of this disclosure.

The figures are not necessarily to scale. Where appropriate, the same orsimilar reference numerals are used in the figures to refer to similaror identical elements. For example, reference numerals utilizinglettering (e.g., job 420 a, job 420 b) refer to instances of the samereference numeral that does not have the lettering (e.g., jobs 420).

DETAILED DESCRIPTION

Some examples of the present disclosure relate to a distributed weldmonitoring system with job tracking. Conventional weld monitoringsystems require operators to provide monitoring input in order to workeffectively. Conventionally, the monitoring input would be entered at alocal monitoring station. However, the local monitoring stations aredesigned to be stationary and may be difficult to transport.Additionally, some work environments are relatively large. In suchenvironments, welding equipment may be located at a significant distancefrom the local monitoring station, necessitating either moving the localmonitoring station, or a long commute between the welding equipment andthe local monitoring station.

The present disclosure contemplates a distributed weld monitoring systemthat allows welding operators to provide monitoring input via alightweight, handheld user device, such as a mobile device (e.g., asmartphone, tablet, laptop, personal digital assistant, etc.), forexample. The user device may in turn communicate the monitoring input toa central monitoring station. Such a distributed monitoring systemremoves the necessity of long commutes or heavy lifting, allowing anoperator to use a convenient lightweight device to enter monitoringinput instead.

In some examples, the distributed weld monitoring system organizesmonitoring data around a particular job and/or job session. For example,the job may be the construction of a vehicle chassis for a large earthmover. In such an example, each job session might correspond to a periodof time that an operator works on the vehicle chassis. As anotherexample, the job might be the construction of the entire earth mover,and each job session might correspond to a period of time than anoperator works on any aspect of the earth mover. In some examples, eachjob is associated with multiple job sessions. In some examples, each jobsession is associated with a single job, a single welding device, and/ora single operator. By organizing the monitoring data according to jobsand job sessions when collecting the monitoring data, it becomespossible to view and/or analyze the monitoring data according to eachjob and/or job session after the job is over. For example, thedistributed weld monitoring system may be able to determine how muchtime, material, and/or other resources were spent to complete the job(and/or one or more particular job sessions), which may be used forbilling, accounting, quality assurance, performance review, futureplanning, etc.

In some examples, the job and job session data collection may also allowfor monitoring data analysis while the job is still ongoing. Forexample, the distributed weld monitoring system may estimate acompletion percentage of the job while the job is ongoing. For example,the job may be estimated to require a certain amount of one or more jobparameters (e.g., man hours, arc or welding time, number of welds,amount of deposition material, etc.). In such an example, thedistributed weld monitoring system may be able to estimate a completionpercentage based on a comparison of the estimated job requirement(s) andthe recorded job data.

Because the distributed weld monitoring system works best when operatorsregularly provide monitoring input, in some examples, the distributedweld monitoring system may take steps to encourage operator input. Insome examples, this encouragement may take the form of disabling one ormore welding devices that the operator is using until operator input isforthcoming.

FIG. 1 shows an example welding system 100 and local monitoring station200. As shown, the welding system 100 includes a welding torch 118 andwork clamp 117 coupled to a welding-type power supply 108. As shown, thelocal monitoring station 200 is electrically coupled to (and/or inelectrical communication with) the welding-type power supply 108. Insome examples, the local monitoring station 200 may also be incommunication with the welding torch 118 (e.g., via the welding-typepower supply 108).

In the example of FIG. 1 , an operator 116 is handling the welding torch118 near a welding bench 112. In some examples, the welding bench 112may be and/or include a fixturing system configured to hold one or moreworkpiece(s) 110. In some examples the fixturing system may include oneor more work clamps 117 (e.g., manual and/or pneumatic clamps). In someexamples, the workpiece(s) 110 may be independent of a welding bench112, such as, for example a freestanding element such as a structuralsteel element, pipeline, or bridge. While a human operator 116 is shownin FIG. 1 , in some examples, the operator 116 may be a robot and/orautomated welding machine.

In the example of FIG. 1 , the welding torch 118 is coupled to thewelding-type power supply 108 via a welding cable 126. A clamp 117 isalso coupled to the welding-type power supply 108 via a clamp cable 115.The welding-type power supply 108 is, in turn, in communication withlocal monitoring station 200, such as via conduit 130. In some examples,the welding-type power supply 108 may alternatively, or additionally,include wireless communication capabilities (e.g., wirelesscommunication circuitry), through which wireless communication may beestablished with local monitoring station 200.

In the example of FIG. 1 , the welding torch 118 is a gun configured forgas metal arc welding (GMAW). In some examples, the welding torch 118may comprise an electrode holder (i.e., stinger) configured for shieldedmetal arc welding (SMAW). In some examples, the welding torch 118 maycomprise a torch and/or filler rod configured for gas tungsten arcwelding (GTAW). In some examples, the welding torch 118 may comprise agun configured for flux-cored arc welding (FCAW). In some examples, thewelding torch 118 may additionally, or alternatively, comprise a fillerrod. In the example of FIG. 1 , the welding torch 118 includes a trigger119. In some examples, the trigger 119 may be activated by the operator116 to trigger a welding-type operation (e.g., arc).

In the example of FIG. 1 , the welding-type power supply 108 includes(and/or is coupled to) a wire feeder 140. In some examples, the wirefeeder 140 houses a wire spool that is used to provide the welding torch118 with a wire electrode (e.g., solid wire, cored wire, coated wire).In some examples, the wire feeder 140 further includes motorized rollersconfigured to feed the wire electrode to the torch 118 (e.g., from thespool) and/or retract the wire electrode from the torch 118 (e.g., backto the spool).

In the example of FIG. 1 , the welding-type power supply 108 alsoincludes (and/or is coupled to) a gas supply 142. In some examples, thegas supply 142 supplies a shielding gas and/or shielding gas mixtures tothe welding torch 118 (e.g., via cable 126). A shielding gas, as usedherein, may refer to any gas (e.g., CO2, argon) or mixture of gases thatmay be provided to the arc and/or weld pool in order to provide aparticular local atmosphere (e.g., shield the arc, improve arcstability, limit the formation of metal oxides, improve wetting of themetal surfaces, alter the chemistry of the weld deposit, and so forth).

In the example of FIGS. 1 and 2 , the welding-type power supply 108 alsoincludes an operator interface 144. In the example of FIG. 1 , theoperator interface 144 comprises one or more adjustable inputs (e.g.,knobs, buttons, switches, keys, etc.) and/or outputs (e.g., displayscreens, lights, speakers, etc.) on the welding-type power supply 108.In some examples, the operator interface 144 may comprise a remotecontrol and/or pendant. In some examples, the operator 116 may use theoperator interface 144 to enter and/or select one or more weldparameters (e.g., voltage, current, gas type, wire feed speed, workpiecematerial type, filler type, etc.) and/or weld operations for thewelding-type power supply 108. In some examples, the operator interface144 may further include one or more receptacles configured forconnection to (and/or reception of) one or more external memory devices(e.g., floppy disks, compact discs, digital video disc, flash drive,etc.).

In the example of FIG. 1 , the welding-type power supply 108 includespower conversion circuitry 132 configured to receive input power (e.g.,from mains power, a generator, etc.) and convert the input power towelding-type output power. In some examples, the power conversioncircuitry 132 may include circuit elements (e.g., transformers,rectifiers, capacitors, inductors, diodes, transistors, switches, and soforth) capable of converting the input power to output power. In someexamples, the power conversion circuitry 132 may also include one ormore controllable circuit elements. In some examples, the controllablecircuit elements may comprise circuitry configured to change states(e.g., fire, turn on/off, close/open, etc.) based on one or more controlsignals. In some examples, the state(s) of the controllable circuitelements may impact the operation of the power conversion circuitry 132,and/or impact characteristics (e.g., current/voltage magnitude,frequency, waveform, etc.) of the output power provided by the powerconversion circuitry 132. In some examples, the controllable circuitelements may comprise, for example, switches, relays, transistors, etc.In examples where the controllable circuit elements comprisetransistors, the transistors may comprise any suitable transistors, suchas, for example MOSFETs, JFETs, IGBTs, BJTs, etc.

As shown, the welding-type power supply 108 further includes controlcircuitry 134 electrically coupled to and configured to control thepower conversion circuitry 132. In some examples, the control circuitry134 may include processing circuitry (and/or one or more processors) aswell as analog and/or digital memory. In some examples, the controlcircuitry 134 is configured to control the power conversion circuitry132, so as to ensure the power conversion circuitry 132 generates theappropriate welding-type output power for carrying out the desiredwelding-type operation.

In some examples, the control circuitry 134 is also electrically coupledto and/or configured to control the wire feeder 140 and/or gas supply142. In some examples, the control circuitry 134 may control the wirefeeder 140 to output wire at a target speed and/or direction. Forexample, the control circuitry 134 may control the motor of the wirefeeder 140 to feed the wire electrode to (and/or retract the wireelectrode 250 from) the torch 118 at a target speed. In some examples,the welding-type power supply 108 may control the gas supply 142 tooutput a target type and/or amount gas. For example, the controlcircuitry 134 may control a valve in communication with the gas supply142 to regulate the gas delivered to the welding torch 118.

In the example of FIG. 1 , the welding system 100 further includesseveral sensors 150. In some examples, the sensors 150 may be configuredto sense, detect, and/or measure various welding data of the weldingsystem 100. For example, the sensors 150 may sense, detect, and/ormeasure a voltage and/or current of the power received by thewelding-type power supply 108, power conversion circuitry 132, and/orwelding torch, and/or the voltage and/or current of the power output bythe welding-type power supply 108 and/or power conversion circuitry 132.As another example, the sensors 150 may sense, detect, and/or measure avelocity (e.g., speed and/or feed direction) of the wire feeder 140and/or type of wire being fed by the wire feeder 140. As anotherexample, the sensors 150 may sense, detect, and/or measure a gas typeand/or gas flow (e.g., through a valve) from the gas supply 142 to thewelding torch 118. As another example, the sensors 150 may sense,detect, and/or measure a trigger signal (e.g., pull, release, etc.) ofthe welding torch 118, and/or a clamping signal (e.g., clamp, unclamp,etc.) of the clamp 117. In some examples, the control circuitry 134 maybe in communication with the sensors 150 and/or otherwise configured toreceive information from the sensors 150.

In some examples, a welding operation (and/or welding process) may beinitiated when the operator 116 activates the trigger 119 of the weldingtorch 118 (and/or otherwise activates the welding torch 118). During thewelding operation, the welding-type power provided by the welding-typepower supply 108 may be applied to the electrode (e.g., wire electrode)of the welding torch 118 in order to produce a welding arc between theelectrode and the one or more workpieces 110. The heat of the arc maymelt portions of a filler material (e.g., wire) and/or workpiece 110,thereby creating a molten weld pool. Movement of the welding torch 118(e.g., by the operator) may move the weld pool, creating one or morewelds 111.

When the welding operation is finished, the operator 116 may release thetrigger 119 (and/or otherwise deactivate the welding torch 118). In someexamples, the control circuitry 134 may detect that the weldingoperation has finished. For example, the control circuitry 134 maydetect a trigger release signal via sensor 150. As another example, thecontrol circuitry 134 may receive a torch deactivation command via theoperator interface 144 (e.g., where the torch 118 is maneuvered by arobot and/or automated welding machine).

In some examples, the control circuitry 134 may detect (e.g., viasensors 150) certain welding data pertaining to the welding-type powersupply 108, clamp 117, bench 112, and/or welding torch 118 during awelding process. In some examples, the control circuitry 134 isconfigured to communicate this welding data (e.g., via a data transferobject (dto)) to the local monitoring station 200. In some examples, thecontrol circuitry 134 may be configured to communicate the welding datato the local monitoring station 200 in real time, periodically during awelding operation, and/or after a welding operation.

FIG. 2 shows the example local monitoring station 200 electrically(and/or communicatively) coupled to several example welding-type powersupplies 108 and/or welding torches 118. As shown, the local monitoringstation 200 is also electrically (and/or communicatively) coupled to auser interface (UI) 202 and a local data repository 204. In someexamples, the local data repository 204 comprises a database. In someexamples, the local data repository 204 is configured to store and/ororganize welding data, monitoring input entered by an operator 116 (orother individual), and/or other relevant information.

In some examples, the user interface 202 may comprise a touch screeninterface and/or one or more input devices (e.g., mouse, keyboard,buttons, knobs, microphones, etc.) and/or output devices (e.g., displayscreen, speakers, etc.). In some examples, the user interface 202 mayfurther include one or more receptacles configured for connection to(and/or reception of) one or more external memory devices (e.g., floppydisks, compact discs, digital video disc, flash drive, etc.). Inoperation, an operator 116 or other user may provide input to, and/orreceive output from, the local monitoring station 200 via the userinterface 202. While shown as a separate component in the example ofFIG. 2 , in some examples, the UI 202 and/or local data repository 204may be part of the local monitoring station 200.

FIG. 2 additionally shows example components of the local monitoringstation 200. As shown, the local monitoring station 200 includescommunication circuitry 206, processing circuitry 208, and memory 210,interconnected with one another via a common electrical bus. In someexamples, the processing circuitry 208 may comprise one or moreprocessors. In some examples, the communication circuitry 206 mayinclude one or more wireless adapters, wireless cards, cable adapters,wire adapters, dongles, radio frequency (RF) devices, wirelesscommunication devices, Bluetooth devices, IEEE 802.11-compliant devices,WiFi devices, cellular devices, GPS devices, Ethernet ports, networkports, lightning cable ports, cable ports, etc. In some examples, thecommunication circuitry 206 may be configured to facilitatecommunication via one or more wired media and/or protocols (e.g.,Ethernet cable(s), universal serial bus cable(s), etc.) and/or wirelessmediums and/or protocols (e.g., near field communication (NFC), ultrahigh frequency radio waves (commonly known as Bluetooth), IEEE 802.11x,Zigbee, HART, LTE, Z-Wave, WirelessHD, WiGig, etc.). In some examples,the local monitoring station 200 may be implemented by way of a desktopcomputer or local server computer. In some examples, the memory 210 maystore the local data repository 204. In the example of FIG. 2 , thememory stores a local monitoring program 800, further discussed below.

FIG. 3 shows an example of a distributed weld monitoring system 300. Asshown, the distributed weld monitoring system 300 comprises a centralmonitoring station 302 electrically (and/or communicatively) coupled toseveral local monitoring stations 200, each of which is electrically(and/or communicatively) coupled to several welding devices 399. In someexamples, each welding device 399 comprises a welding-type power supply108, an output of a welding-type power supply 108 (e.g., for a multipleoutput welding-type power supply 108), a welding torch 118, a gas supply142, a wire feeder 140, a clamp 117, and/or one or more otherwelding-type devices (e.g., a polishing device, sanding device,induction heating device, etc.). In the example of FIG. 3 , the centralmonitoring station 302 is further electrically (and/or communicatively)coupled to central data repository 400.

In the example of FIG. 3 , the central monitoring station 302 isadditionally communicatively coupled to a user device 350. While onlyone user device 350 is depicted in the example of FIG. 3 for the sake ofsimplicity, in some examples a plurality of user devices may be incommunication with the central monitoring station 302. In some examples,the user device 350 may be implemented by way of a mobile device (e.g.,a smartphone, tablet, laptop, personal digital assistant, etc.).

In the example of FIG. 3 , the user device 350 includes communicationcircuitry 356, processing circuitry 358, memory 360, and a human machineinterface (HMI) 352 interconnected with one another via a commonelectrical bus. In some examples, the processing circuitry 358 maycomprise one or more processors. In some examples, the communicationcircuitry 356 may include one or more wireless adapters, wireless cards,cable adapters, wire adapters, dongles, radio frequency (RF) devices,wireless communication devices, Bluetooth devices, IEEE 802.11-compliantdevices, WiFi devices, cellular devices, GPS devices, Ethernet ports,network ports, lightning cable ports, cable ports, etc. In someexamples, the communication circuitry 356 may be configured tofacilitate communication via one or more wired media and/or protocols(e.g., Ethernet cable(s), universal serial bus cable(s), etc.) and/orwireless mediums and/or protocols (e.g., near field communication (NFC),ultra high frequency radio waves (commonly known as Bluetooth), IEEE802.11x, Zigbee, HART, LTE, Z-Wave, WirelessHD, WiGig, etc.).

In some examples, the HMI 352 may comprise a touch screen interfaceand/or one or more input devices (e.g., keyboard, buttons, knobs,microphones, etc.) and/or output devices (e.g., display screen,speakers, etc.). In some examples, the HMI 352 may further include oneor more receptacles configured for connection to (and/or reception of)one or more external memory devices (e.g., floppy disks, compact discs,digital video discs, flash drives, etc.). In operation, an operator 116or other user may provide input (e.g., monitoring input) to, and/orreceive output from, the user device 350 via the HMI 352. In the exampleof FIG. 3 , the memory stores a user device monitoring program 600,further discussed below.

FIG. 3 additionally shows example components of the central monitoringstation 302. As shown, the central monitoring station 302 includescommunication circuitry 306, processing circuitry 308, and memory 310,interconnected with one another via a common electrical bus. In someexamples, the processing circuitry 308 may comprise one or moreprocessors. In some examples, the communication circuitry 306 mayinclude one or more wireless adapters, wireless cards, cable adapters,wire adapters, dongles, radio frequency (RF) devices, wirelesscommunication devices, Bluetooth devices, IEEE 802.11-compliant devices,WiFi devices, cellular devices, GPS devices, Ethernet ports, networkports, lightning cable ports, cable ports, etc. In some examples, thecommunication circuitry 306 may be configured to facilitatecommunication via one or more wired media and/or protocols (e.g.,Ethernet cable(s), universal serial bus cable(s), etc.) and/or wirelessmediums and/or protocols (e.g., near field communication (NFC), ultrahigh frequency radio waves (commonly known as Bluetooth), IEEE 802.11x,Zigbee, HART, LTE, Z-Wave, WirelessHD, WiGig, etc.). In some examples,the central monitoring station 302 may be implemented by way of adesktop computer or central server computer. In some examples, thememory 310 may store the central data repository 400. In the example ofFIG. 3 , the memory 310 stores a central monitoring program 700, furtherdiscussed below.

FIG. 4 shows a more detailed example of the central data repository 400.In some examples, the central data repository 400 and local datarepository 204 may be similarly (or identically structured). In someexamples, the central data repository 400 and/or local data repository204 may be implemented via one or more databases, database tables,and/or other data structures.

In the example of FIG. 4 , the central data repository 400 storeswelding device information 402, user information 404, activityinformation 406, and custom field information 408. In some examples, thecentral data repository 400 may also include additional information,such as, for example, local monitoring station information, centralmonitoring station information, and/or other relevant information. Insome examples, the welding device information 402, user information 404,activity information 406, custom field information 408, and/or otherinformation may be modified by user input (e.g., by a user with certainadministrative privileges via the user device 350 and/or localmonitoring station 200), programmatic input, and/or other appropriatemechanisms.

In some examples, the welding device information 402 may include one ormore welding device identifiers. In some examples, each welding deviceidentifier may be uniquely associated with a specific welding device399, as well as information about that welding device 399, such as, forexample, device type (e.g., MIG gun, TIG torch, wire feeder, ACwelding-type power supply, DC welding-type power supply, gas supply,etc.), device location, approved users for device, approved jobs fordevice, associated local monitoring station 200, manufacturer, modelnumber, serial number, maintenance history, software revisions, etc. Insome examples, the user information 404 may include one or more useridentifiers. In some examples, each user identifier 452 may beassociated with a particular user (e.g., an operator 116), as well asinformation about the user, such as, for example, name, age, experience,certifications, certification levels, approved devices for user,approved jobs for user, login credentials, work schedule(s), traininghistory, operational history, assigned tasks, assigned workflow items,assigned work orders, etc.

In some examples, the activity information 406 may include informationabout various known activities and/or recorded activities that takeplace during a job session 450. Such activities might include, forexample, welding device related activities (e.g., normal operation,maintenance operation, startup operation, shutdown operation, etc.),maintenance activities, quality assurance activities, resupplyactivities, replacement activities, break activities, error relatedactivities, training activities, meeting activities, and/or otheractivities. In some examples, some or all of the activities may beassociated with one or more timestamps, identifying dates and/or timeswhen the activities have occurred and/or are expected to occur. In someexamples, some or all of the activities may be associated with one ormore custom fields. In some examples, each activity may be uniquelyassociated with an activity identifier.

In some examples, the custom field information 408 may includeinformation about various custom fields used by the distributed weldmonitoring system 300. In some examples, the custom field information408 may include one or more custom field identifiers. In some examples,each custom field identifier may be uniquely associated with aparticular custom field. In some examples, the custom field information408 may include other information about each custom field, such as, forexample, name, type (e.g., Boolean, text, drop down list, numerical,date, checkbox, radio button, etc.), entry options (e.g., options fordrop down, checkboxes, radio buttons, etc.), prompt(s) (e.g., enter:wire feed speed, wire type, wire size, gas type, work order identifier,operator certification level, workpiece material, joint number,operational suggestions, operational problems, corrective actions, notesfor management, etc.), description, obligation (e.g., required/optionalfor everyone or particular users/jobs/devices, etc.), associated jobs420, associated activities, associated users, associated welding devices399, and/or other relevant information.

In some examples, custom fields may be associated with different jobs420, welding devices 399, users, activities, etc. to collect differentinformation from a user depending on the job 420, welding device 399,user, activity, etc. For example, a user (and/or administrator) mightcreate a numerical custom field and associated prompt asking for wiresize, and associate the custom field with all wire feeder weldingdevices 399. In such an example, any time a user starts a job session450 and specifies a wire feeder as the welding device 399, the wire sizecustom field and prompt will be presented. As another example, a user(and/or administrator) might create a Boolean custom field andassociated prompt asking if a certain certification level has beenreached, and associate the custom field with certain jobs 420 (e.g.,more complex jobs). In such an example, any time a user starts a jobsession 450 for that particular job 420, the certification level customfield and prompt will be presented. In some examples, entries into thecustom fields (i.e., custom field entries 456) may be stored withincentral data repository 400 (and/or local data repository) and/orassociated with a particular job session 450.

FIG. 5 shows an example custom field setup screen 500. In some examples,the custom field setup screen 500 may be presented to a user (e.g., auser with administrative privileges) during a setup of the distributedweld monitoring system 300. As shown, the custom field setup screen 500allows for entry of a name, description, help information, and fieldtype. As shown, the custom field setup screen 500 also allows for thecustom field to be marked as either required or optional, via the button502.

In the example of FIG. 4 , the central data repository 400 also storesdata relating to several jobs 420. As shown, each job 420 comprisesseveral job sessions 450. FIG. 4 further illustrates example monitoringdata associated with each job 420 and job session 450. As shown, eachjob 420 is associated with a job identifier 422, one or more sessionidentifiers 424, open/close timestamps 426, approved users 428, andapproved welding devices 430.

As shown, each job session 450 is associated with open/close timestamps426, a user identifier 452, a job identifier 422, a session identifier424, custom fields 454, custom field entries 456, device data 458, andactivity data 460. In some examples, the custom fields 454 may be storedas part of the overall job 420 rather than, or in addition to, theindividual job session 450. In some examples, each job 420 and/or jobsession 450 may be associated more or less data than shown in theexample of FIG. 4 . For example, each job 420 may be associated with atextual description of the job 420, a due date, specifications,schematics, estimated number of man hours and/or arc time to complete,budget, and/or other information and/or materials pertaining to the job420.

In some examples, each job 420 is associated with a job identifier 422that is not associated with any other job 420. In some examples, eachjob session 450 is associated with a job session identifier 424 that isnot associated with any other job session 450. In some examples, eachuser is associated with a user identifier 452 that is not associatedwith any other user. In some examples, each welding device 399 isassociated with a welding device identifier that is not associated withany other welding device 399. In some examples, each job identifier 422,user identifier 452, and/or device identifier, may be automaticallygenerated by the central data repository 400, local data repository 204,central monitoring station 302, or local monitoring station 200.

In some examples, one or more (or no) job sessions 450 may be associatedwith a job 420 through the session identifiers 424 of the job 420. Insome examples, one or more (or no) users may be associated with a job420 through the approved users 428 of the job 420. In some examples, oneor more (or no) welding devices 399 may be associated with a job 420through the approved welding devices 430 of the job 420. In this way,the monitoring data of the distributed weld monitoring system 300 can beorganized according to jobs 420 and job sessions 450.

In some examples, the open/close timestamps 426 of each job 420 and/orjob session 450 may comprise timestamps representative of a date and/ortime when the job 420 and/or job session 450 is opened and/or closed. Insome examples, each opened job 420 and/or job session 450 may have anopen timestamp. However, in some examples, a job 420 and/or job session450 may only have a close timestamp if the job 420 and/or job session450 has been closed. Thus, in some examples, a job 420 and/or jobsession 450 that is still open may have no close timestamp, so as toidentify the job 420 and/or job session 450 as open. In some examples,each job 420 and/or job session 450 may additionally, or alternatively,be associated with an explicit flag that indicates whether the job 420and/or job session 450 is open or closed.

In some examples, the approved users 428 for each job 420 comprises dataidentifying (e.g., via user identifier 452) one or more operators 116that are approved to work on the job 420. In some examples, thisinformation may be used by the distributed weld monitoring system 300 todetermine what jobs 420 to present to a user as options when beginning ajob session 450, compiling reports, performing analysis, etc. In someexamples, the approved welding devices 430 for each job 420 comprisesdata identifying (e.g., via welding device identifier) one or morewelding devices 399 that are approved for the job 420. In some examples,this data may be used by the distributed weld monitoring system 300 todetermine what welding devices 399 to present to a user as options whenbeginning a job session 450, compiling reports, performing analysis,etc.

In the example of FIG. 4 , each job session 450 is associated with asingle user (e.g., via user identifier 452) and single job 420 (e.g.,via job identifier 422). In some examples, each job session 450 is onlyassociated with a single user, and no job session 450 may be associatedwith more than one user. In some examples, each job session 450 is alsoassociated with only a single job 420, and no job session 450 may beassociated with more than one job 420.

In the example of FIG. 4 , each job session 450 is also associated withone or more (or no) custom fields 454. In some examples, each customfield 454 associated with a job session 450 (and/or job 420) is alsoassociated with one of the custom fields of the custom field information408. The custom field entries 456 shown in FIG. 4 as part of the jobsession 450 comprise entries inputted by a user in the one or morecustom fields 454 (e.g., via the HMI 352 of a user device 350).

In the example of FIG. 4 , each job session 450 is associated withwelding device data 458. In some examples, each job session 450 may beassociated with a single welding device 399 (or no welding device 399),and no job session 450 may be associated with more than one weldingdevice 399. In some examples, the welding device data 458 may includedata identifying the single welding device 399 associated with the jobsession 450, to the extent there is such a welding device 399. Forexample, the welding device data 458 may include a welding deviceidentifier that corresponds to a welding device identifier of thewelding device information 402. In some examples, the welding devicedata 458 may additionally include welding data received from the weldingdevice 399. For example, welding data may be continually collected fromthe welding device 399 by the local monitoring station 200 and stored inthe welding device data 458 of the local data repository 204, which maythen be synched with the welding device data 458 of the central datarepository. In some examples, the welding device data 458 mayadditionally comprise one or more timestamps associated with the weldingdata.

In the example of FIG. 4 , each job session 450 is also associated withactivity data 460. In some examples, the activity data 460 may comprisedata pertaining to one or more activities that occur during the jobsession 450. In some examples, the each activity may be related to thewelding device 399 being used by the operator 116 or to some activity ofthe separate from the welding device 399. In some examples, the activitydata 460 may include one or more timestamps associated with eachactivity (e.g., noting the time period(s) the activity are takingplace). In some examples, one or more activities for each job session450 may be automatically determined by the distributed weld monitoringsystem 300 (e.g., using the known activities stored in the activityinformation 406), selected by the user from several options (e.g.,pulled from the activity information 406), and/or manually input by theuser.

FIG. 6 a is a flowchart illustrating an example user device monitoringprogram 600 of the distributed weld monitoring system 300. In someexamples, the user device monitoring program 600 may be implemented inmachine readable instructions stored in memory 360 of the user device350 and/or executed by the processing circuitry 358 of the user device350. In some examples, the user device monitoring program 600 may be aweb based application, sent to the user device 350 and/or executedthrough a web browser, for example. In some examples, the user devicemonitoring program 600 may communicate (e.g., via communicationcircuitry 356 of the user device 350) with the central monitoringstation 302 and/or the local monitoring station 200 in operation of theuser device monitoring program 600.

In the example of FIG. 6 a , the user device monitoring program 600begins at block 602, where the user logs in using user credentials. Insome examples, the user device 350 may send the credentials to thecentral monitoring station 302 at block 602, and wait for an affirmativeresponse before proceeding to the block 604 of the user devicemonitoring program 600. In some examples, the central monitoring station302 may access the user information 404 of the central data repository400 to verify the user credentials.

In the example of FIG. 6 a , the user device monitoring program 600allows for several options at blocks 604-608 after block 602. At blocks604-608, the user is given the option of either beginning a new jobsession 450 (block 604), being presented with a list of existing jobsessions 450 (block 606), or analyzing the monitoring data stored in thecentral data repository 400. In some examples, the user may be presentedwith more or less options than shown in FIG. 6 a . For example, the usermay be presented with additional administrative options if the usercredentials are associated with certain administrative privileges. Suchadditional administrative options may include, for example, the optionto create and/or edit information (and/or associations) relating to jobs420, welding device information 402, custom fields information 408,activity information 406, local monitoring stations 200, the centralmonitoring station 302, user information 404, user devices 350, and/orother aspects of the distributed weld monitoring system 300 (see, e.g.,FIG. 5 ). As another example, the user may only be given the option ofbeing presented with a list of existing job sessions 450 (block 606), oranalyzing the jobs 420 and/or job sessions 450 if their user credentialsare associated with adequate administrative privileges.

In the example of FIG. 6 a , the user device monitoring program 600proceeds to block 610 if the user selects to start a new job session 450at block 604. Block 610 is further explained below. In the example ofFIG. 6 a , the user device monitoring program 600 proceeds to block 612if the user selects to list existing job sessions 450 at block 606. Atblock 612, the user device sends a query request to the centralmonitoring station 302, receives a response from the central monitoringstation 300 that include result data of the query request, and outputsthe result data to the user via the HMI 352 of the user device 350.

In some examples, the query request sent to the central monitoringstation 300 at block 612 may request data pertaining to one or more jobsessions 450 that meet certain search criteria. In some examples, thesearch criteria may be entered by the user via the HMI 352 of the userdevice 350. In some examples, the search criteria may comprise one ormore jobs 420, welding devices 399, open/close timestamps 426,activities, status (e.g., open or closed), and/or other monitoring data.In some examples, the user's credentials may be automatically includedas part of the search criteria. In some examples, the user (and/or useridentifier 452) may be a selectable search criteria (e.g., where thelogged in user has credentials associated with certain administrativeprivileges).

FIG. 6 b shows an example of a session list screen 620 that might bedisplayed to a user via the HMI 352 of the user device 350 at block 612of the user device monitoring program 600. As shown, the session listtab 624 is selected and emphasized such that it is larger than the newsession tab 622 and analysis tab 626. A user filter 626 has been set to“My Sessions” to automatically use the current login credentials for thesearch criteria. In some examples, the session list screen 620 mightallow for entry of some identification information (e.g., name, useridentifier 452, etc.) of a different operator if “All Sessions” wasinstead selected. As shown, the session list screen 620 further displayssearch criteria fields 628 for job 420, welding device 399, open/closetimestamps 426, and activities. In some examples, more or less searchcriteria fields 628 may be presented.

In the example of FIG. 6 b , a refresh button 630 may be selected tosubmit the query request. As shown, the query request has already beensubmitted, and the data returned by the central monitoring station 300is displayed in a result table 632. In the example of FIG. 6 b , theresult table 632 is organized by rows, with information for the same jobsession 450 displayed in the same row. As shown, each row of the resulttable 632 also includes a selectable edit button 634. In some examples,selection of the edit button 634 may allow a user to make changes tosome or all of the information pertaining to the job session 450corresponding to that row of the result table 632. In some examples, theedit button 634 may only be shown or selectable when the user'scredentials are associated with certain administrative privileges.

In the example of FIG. 6 a , the user device monitoring program 600proceeds to block 614 if the user selects to perform an analysis atblock 608. At block 614 the user device monitoring program 600 providesan analysis of data stored in the central data repository 400. Forexample, the user device 350 may send a query request to the centralmonitoring station 302 (similar to block 612) along with an analysisrequest for a particular analysis to be performed. In some examples, thequery request may use one or more of the search criteria described abovewith respect to block 612.

In some examples, the analysis request may be for a time based analysis,so that the user device monitoring program 600 may present the queryresult data returned from the central monitoring station 302 in a timesynchronized graph, chart, diagram, or other appropriate form showingdata over time. In some examples, the analysis request may be for acomparison of data (e.g., monitoring data for one job 420 a v.monitoring data for another job 420 b). In some examples, the analysisrequest may be for a completion estimation (e.g., percentage complete,percentage incomplete) and/or estimated time to completion (e.g., arctime, man hour time, session time, etc.) of one or more jobs 420. Insome examples, such estimation may be based on recorded information ofthe job 420 (e.g., entered at setup and/or afterwards) and/or monitoringinformation (e.g., arc time, session time, normal device activity time,etc.) recorded by the distributed weld monitoring system 300. In someexamples, the user device monitoring program 600 may receive theanalysis data from the central monitoring station 300 and present theanalysis data to the user via the HMI 352 of the user device 350.

In the example of FIG. 6 a , the user device monitoring program 600proceeds to block 616 after any of blocks 610-614. At block 616, theuser device monitoring program 600 checks whether the user devicemonitoring program 600 should be ended. In some examples, the userdevice monitoring program 600 may be ended at block 616 in response toan explicit request by the user to end the user device monitoringprogram 600 (e.g., by closing the user device monitoring program 600and/or an associated web browser), a logout request by the user, an endcommand received from the central monitoring station 302, and/or otherappropriate action and/or input. If the user device monitoring program600 determines the user device monitoring program 600 should be ended,then an indication that the user device monitoring program 600 is endingmay be sent to the central monitoring station 302, along with anyadditional data necessary, before the user device monitoring program 600ends. If the user device monitoring program 600 determines that the userdevice monitoring program 600 should not be ended, then the user devicemonitoring program 600 returns to block 604.

FIG. 6 c is a flowchart illustrating an example implementation of thestart new job session block 610 of the example user device monitoringprogram 600 of FIG. 6 a . As shown, the start new job session block 610begins at block 640. At block 640, the user device monitoring program600 prompts the user to enter job session data 642, such as, forexample, via one or more input fields presented to the user through theHMI 352 of the user device 350. In some examples, the job session datamay include an identification of a job 420, custom fields 454, customfield entries 456, welding device data 458, activity data 460, and/orother job session data 642. In some examples, some of the job sessiondata may not need to be entered (e.g., no need for welding device data458 if no welding device 399 is being used).

In some examples, the user device monitoring program 600 may require anidentification of the job before allowing the custom field entries,welding device data 458, and/or activity data 460 to be entered. In someexamples, the user device monitoring program 600 may provide the userwith input options and/or input prompts for the custom fields 454,welding device data 458, activity data 460, and/or other job sessiondata 642, such as via a dropdown box, checkboxes, and/or dialog buttons,for example. In some examples, the user device monitoring program 600may send a request to the central monitoring station 302 to obtain theinput options and/or input prompts, such as, for example, in response toa user activating the input field (e.g., clicking a dropdown box) orentry of some other job session data. In some examples, the user devicemonitoring program 600 may provide some or all of the user entered jobsession data 642 to the central monitoring station 302 in response touser entry and/or selection of one or more input options. In someexamples, the input options and/or input prompts provided by the centralmonitoring station 302 may be dependent upon the user (e.g., the user'scredentials and/or associated privileges), and/or the entered jobsession data 640.

In the example of FIG. 6 c , the user device monitoring program 600proceeds to block 644 after block 640. In some examples, the transitionfrom block 640 to block 644 may occur in response to user action, suchas, for example, activation of a start session button 698 (see, e.g.,FIG. 6 d ). In some examples, the user device monitoring program 600 mayrequire completion of some or all of the job session data 642 beforeallowing activation of the start session button 698 and execution ofblock 644. At block 644, the user device monitoring program 600 attemptsto start a new job session 450 using the entered job session data ofblock 640. For example, the user device monitoring program 600 may sendsome or all of the job session data 642 to the central monitoringstation 300 along with a request to start a new job session 450.

In the example of FIG. 6 c , the user device monitoring program 600proceeds to block 646 after block 644. At block 646, the user devicemonitoring program 600 receives a signal from the central monitoringstation 302 indicative of whether the request to start a new job session450 was a success or failure. If it was a failure, then the user devicemonitoring program 600 returns to block 640. If the request to start anew job session 450 was a success, then the user device monitoringprogram 600 begins the job session 450 and proceeds to block 648.

In the example of FIG. 6 c , the user device monitoring program 600retrieves (e.g., requests and/or receives) a job session report from thecentral monitoring station 302 at block 648. In some examples, the userdevice monitoring program 600 may additionally provide information fromthe job session report to the user (e.g., via the HMI 352 of the userdevice 350) at block 648. In some examples, the job session report mayinclude welding data and/or welding related data such as, for example,arc count, consumable cost, deposition amount, current, voltage, wirefeed speed, gas flow, torch work angle, torch travel angle, torch tip towork distance, torch travel speed, torch aim, arc length, and/or otherappropriate parameters relating to operation of the welding device. Insome examples, the job report may additionally, or alternatively,include other information regarding the job session 450, such as, forexample, open/close timestamps 426 of the job session 450, a lastupdated timestamp, an activity, and/or other relevant informationrelating to the job session 450.

In the example of FIG. 6 c , the user device monitoring program 600proceeds to block 650 after block 648. At block 650, the user devicemonitoring program 600 checks whether there is a new activity associatedwith the job session 450, such as communicated by the central monitoringstation 302 or inputted by the user via the HMI 352 of the user device350. If so, then the user device monitoring program 600 updates acurrent activity at block 652. In some examples, updating the currentactivity at block 652 may include sending the current activity to thelocal monitoring station 200 (e.g., via SignalR). In some examples, theuser device monitoring program 600 may request and/or receiveinformation regarding the which local monitoring station 200 to send thecurrent activity at (or before) block 650.

In some examples, the user device monitoring program 600 may receive oneor more custom input fields 454 (and/or custom input prompts), and/orone or more requests for updated custom field entries 456 from thecentral monitoring station 302 and/or local monitoring station 200 inresponse to the updated current activity. In some examples, the userdevice monitoring program 600 may provide the one or more one or morecustom input fields 454 (and/or custom input prompts) to the user viathe HMI 352. In some examples, the user device monitoring program 600may communicate any user inputs relating to the one or more custom inputfields 454 (and/or requests for updated custom field entries 456) to thecentral monitoring station 302. In the example of FIG. 6 c , the userdevice monitoring program 600 repeats block 648 after block 652.

In the example of FIG. 6 c , the user device monitoring program 600proceeds to block 654 if there is no new activity at block 650. At block654, the user device monitoring program 600 checks whether the jobsession 450 should be ended. In some examples, the job session 450 maybe ended at block 654 in response to an explicit request by the user toend the job session 450 (e.g., by activating an end session button), alogout request by the user, an end command received from the centralmonitoring station 302, and/or other appropriate action and/or input. Ifthe user device monitoring program 600 determines the job session 450should be ended at block 654, then an indication that the job session450 should be ended is sent to the central monitoring station 302, alongwith any additional data necessary to end the job session. Afterwards,the user device monitoring program 600 returns to block 616 of FIG. 6 a. If the user device monitoring program 600 determines that the jobsession 450 should not be ended, then the user device monitoring program600 returns to block 648.

FIG. 6 d shows an example new session screen 699 that might be displayedto a user via the HMI 352 of the user device 350 at block 610 of theuser device monitoring program 600. In some examples, the new sessionscreen 699 might be displayed within a web browser of the user device350. As shown, the New Session tab 622 is selected and emphasized suchthat it is larger than the Session List tab 624 and Analysis tab 626. Inthe example of FIG. 6 d , the new session screen 699 includes a jobinput field 696, a welding device input field 694, an activity inputfield 688, and several custom field prompts 692 and custom input fields690. As shown, the job input field 696, welding device input field 694,and activity input field 688 are dropdown boxes, while the custom inputfields 690 include a dropdown box, a numerical field, and an on/off(i.e., Boolean) button. The new session screen 699 further includes aninformation panel 686 that can be updated during the job session 450with information pertaining to the job session 450. The new sessionscreen 699 further includes a start session button 698 that may beactivated by a user to start the job session 450. In some examples, thestart session button 698 may become an end session button after thesession is started.

FIG. 7 a is a flowchart illustrating an example central monitoringprogram 700 of the central monitoring station 302. In some examples, thecentral monitoring program 700 may be implemented in machine readableinstructions stored in memory 310 of the central monitoring station 302and/or executed by the processing circuitry 308 of the centralmonitoring station 302. In some examples, multiple instances of thecentral monitoring program 700 may execute at the same time, so as toaccommodate multiple user devices 350 and/or instances of the userdevice monitoring program 600. In some examples, the central monitoringprogram 700 may communicate (e.g., via communication circuitry 306 ofthe central monitoring station 302) with the local monitoring station200 and/or the user device 350 in operation of the central monitoringprogram 700.

In the example of FIG. 7 a , the central monitoring program 700 beginsat block 702. At block 702, the central monitoring program 700 receivesuser credentials from a user device 350 and either authenticates theuser credentials (e.g., using the user information 404 of the centraldata repository 400) or rejects the user credentials after failing toauthenticate. In either case, the central monitoring program 700 sendsone or more corresponding signals to the user device 350 representativeof the user authentication result.

In the example of FIG. 7 a , the central monitoring program 700 proceedsto block 704 after block 702. At blocks 704-708, the central monitoringprogram 700 responds to requests received from the user device 350(e.g., via one or more signals) to begin a new job session 450 (block704), handle a query (block 706), and/or handle analysis (block 708). Insome examples, the central monitoring program 700 may be configured torespond to more or fewer requests. For example, the central monitoringprogram 700 may be configured to respond to one or more signalsindicative of one or more administrative requests if the usercredentials are associated with certain administrative privileges. Suchadditional administrative requests may include, for example, a requestto create and/or edit information (and/or associations) relating to jobs420, job sessions 450, welding device information 402, user information404, activity information 406, custom field information 408, localmonitoring stations 200, the central monitoring station 302, userdevices 350, and/or other aspects of the distributed weld monitoringsystem 300 (see, e.g., FIG. 5 ). In some examples, the centralmonitoring program 700 may respond negatively (e.g., with an error,refusal, denial, etc.) to administrative, query, and/or analysisrequests if the user credentials received at block 702 are notassociated with adequate administrative privileges.

In the example of FIG. 7 a , the central monitoring program 700 proceedsto block 710 if a request is received (e.g., from the user device 350)to start a new job session 450 at block 704. Block 710 is furtherexplained below. In the example of FIG. 7 a , the central monitoringprogram 700 proceeds to block 712 if a query request is received atblock 706. At block 712, the central monitoring program 700 receives thequery request along with search criteria on which the query is to bebased, and performs the query on the central data repository 400 usingthe search criteria. The central monitoring program 700 then sends thequery results back to the user device 350.

In the example of FIG. 7 a , the central monitoring program 700 proceedsto block 714 if an analysis request is received at block 708. At block714 the central monitoring program 700 receives a query request alongwith search criteria and an analysis request. The central monitoringprogram 700 performs the query using the search criteria, similar toblock 712, and the central data repository 400 returns query result datain response to the query. The central monitoring program 700 furtherformats, structures, and/or processes the query result data based on theanalysis request, so that the query result data may be appropriatelypresented to the user in a useful and/or actionable format. For example,the central monitoring program 700 may receive an analysis request fortime synchronized query result data, and the central monitoring program700 may format and/or structure the query result data such that thequery result data may be presented in a time synchronized graph, chart,diagram, or other appropriate form showing data over time. As anotherexample, the analysis may be for a comparison of data, and the centralmonitoring program 700 format and/or structure the query result datasuch that the query result data may be presented in a graph, chart,diagram, or other appropriate form showing a comparison of the databased on or more criteria (e.g., identified in the analysis request). Asanother example, the analysis may be for a completion estimation (e.g.,percentage complete, percentage incomplete) and/or estimated time tocompletion (e.g., arc time, man hour time, session time, etc.) of one ormore jobs 420. In such an example, the central monitoring program 700may query the central data repository 400 to determine how much time(e.g., arc time, session time, normal device activity time, etc.) thejob 420 is estimated to require and/or how much time has been recordedfor the job 420 (e.g., in all its associated job sessions 450, somedate/time limited portion of associated job sessions 450, etc.), andreturn analysis results based on this processing.

In the example of FIG. 7 a , the central monitoring program 700 proceedsto block 716 after any of blocks 710-714. At block 716, the centralmonitoring program 700 checks whether the central monitoring program 700should be ended. In some examples, the central monitoring program 700may be ended at block 716 in response to an explicit request by theuser, a logout request by the user, and/or other appropriate actionand/or input. If the central monitoring program 700 determines thecentral monitoring program 700 should be ended, then an indication thatthe user device monitoring program 600 is ending may be sent to the userdevice 350 and/or local monitoring station 200, along with anyappropriate information. If the central monitoring program 700determines that the central monitoring program 700 should not be ended,then the central monitoring program 700 returns to block 704.

FIG. 7 b is a flowchart illustrating an example implementation of thestart new job session block 710 of the example central monitoringprogram 700 of FIG. 7 a . As shown, the start new job session block 710begins at block 720. At block 720, the central monitoring program 700sends job session data 642 to the user device 350. For example, thecentral monitoring program 700 may provide one or more jobs 420available for selection by the user. The central monitoring program 700additionally receives job session data 642 from the user device 350,such as, for example, a selection (and/or identification) of a job 420.In some examples, multiple iterations of sending and receiving jobsession data 642 (e.g., custom fields 454, custom field entries 456,welding device data 458, activity data 460, and/or other job sessiondata 642) may occur at block 720. In some examples, some of the jobsession data may not need to be received (e.g., no need for weldingdevice data 458 if operator 116 is not using a welding device 399).

In some examples, the central monitoring program 700 may also provideselection options (e.g., for custom field entries 456, welding devicedata 458, activity data 460, and/or other job session data 642) and/orcustom fields 454 based on the provided job session data 642 and/or theuser credentials at block 720. In some examples, this may occur inresponse to a user activating an input field (e.g., clicking a dropdownbox) or entry of some job session data 642. In some examples, thecentral monitoring program 700 may query the central data repository 400to determine the one or more selection options and/or custom fields 454.In such an example, the central monitoring program 700 may use as searchcriteria the user credentials (and/or associated privileges) and/or someor all of the received job session data 642. For example, the centralmonitoring program 700 may receive a request for selections options fora welding device 399, and the central monitoring program 700 may querythe central data repository 400 (e.g., the welding device information402) to determine what welding devices 399 may be used given the currentuser and/or currently selected job 420. The result data from the querymay then be sent to the user device 350 in response to the request.

In the example of FIG. 7 b , the central monitoring program 700 proceedsto block 724 after block 720. At block 724, the central monitoringprogram 700 checks whether a request to start a new session has beenreceived. If such a request has not been received, the centralmonitoring program 700 returns to block 720. If a request to start a newsession has been received, the central monitoring program proceeds toblock 725.

In the example of FIG. 7 b , the central monitoring program 700determines whether there is already an open job session 450 with theentered job session data 642 from block 720. In some examples, thisdetermination may comprise querying the central data repository 400 tosee if there is a job session 450 associated certain search criteria,such as, for example, user credentials and/or one or more of the enteredjob session data 642 entered at block 720 (e.g., welding device data458). If there is such a job session 450, the central monitoring program700 may then determine whether the job session 450 is open, such as if,for example, the job session 450 has an open timestamp and no closetimestamp (e.g., in the open/close timestamp 426).

In the example of FIG. 7 b , the central monitoring program 700 returnsto block 720 and sends an error signal (and/or reason for the error) tothe user device 350 if there is an open job session 450 associated withthe search criteria. If there is no open job session 450 associated withthe search criteria, the central monitoring program 700 proceeds toblock 728. At block 728, the central monitoring program 700 creates anew job session 450 in the central data repository 400, using the jobsession data 642 entered at block 720. In some examples, the centralmonitoring program 700 may also send a signal to the user device 350indicative of a successful creation of the new job session 450.

In the example of FIG. 7 b , the central monitoring program 700 proceedsto block 730 after block 728. At block 730, the central monitoringprogram 700 synchronizes the central data repository 400 with the localdata repository 204. In some examples, the synchronization at block 730may occur in response to a synchronization request from the localmonitoring station 200 (and/or local data repository 204), a job reportrequest from the user device 350, and/or an expiration of a thresholdsynchronization time period (e.g., stored in memory 310 and/or thecentral data repository 400). In some examples, the central datarepository 400 may need to be synchronized with the local datarepository 204 to retrieve welding data received at the local datarepository 204 from the welding device 399 associated with the jobsession 450. In some examples, the central monitoring program 700 maydetermine which local monitoring station 200 to synchronize with basedon the welding device 399 associated with the newly created job session450. Additionally, the local monitoring station 200 may perform activitytracking functions, and store the activity related data in the localdata repository 204 until synchronization. In examples where there is nowelding device 399 associated with the new job session 450, the centralmonitoring program 700 may synchronize with a default or most recentlocal monitoring station 200.

In the example of FIG. 7 b , the central monitoring program 700 proceedsto block 732 after block 730. At block 732, the central monitoringprogram 700 sends a job session report to the user device 350. In someexamples, the job session report may include activity trackinginformation, welding data, timestamp information, and/or other dataassociated with the job session 450. In some examples, the job sessionreport sent to the user device 350 at block 732 may be used by the userdevice 350 to update its information panel 686 and/or otherwise bepresented to the user.

In the example of FIG. 7 b , the central monitoring program 700 proceedsto block 734 after block 732. At block 734, the central monitoringprogram 700 determines whether the job session 450 should be ended. Insome examples, the central monitoring program 700 may determine the jobsession 450 should be ended at block 734 in response to signal from theuser device 350 to requesting to end the job session 450, adetermination that the job 420 associated with the job session 450 hasended, and/or other appropriate action and/or input. If the centralmonitoring program 700 determines the job session should not be ended,the central monitoring program 700 returns to block 730. If the centralmonitoring program 700 determines the job session 450 should be ended,the central monitoring program 700 proceeds to block 736.

In the example of FIG. 7 b , the central monitoring program 700 closesthe job session 450 at block 736. In some examples, the centralmonitoring program 700 may send a signal indicative of the closure tothe user device 350 and/or local monitoring station 200, along with anynecessary data. After block 736, the central monitoring program 700returns to block 716 of FIG. 7 a.

FIG. 8 a is a flowchart illustrating an example local monitoring program800 of the local monitoring station 200. In some examples, the localmonitoring program 800 may be implemented in machine readableinstructions stored in memory 210 of the local monitoring station 200and/or executed by the processing circuitry 208 of the local monitoringstation 200. In some examples, the local monitoring program 800 maycommunicate (e.g., via communication circuitry 206 of the localmonitoring station 200) with the central monitoring station 302 and/orone or more welding devices 399 in operation of the local monitoringprogram 800. In some examples, multiple instances of the localmonitoring program 800 may execute at the same time, so as toaccommodate multiple welding devices 399 and/or multiple instances ofthe central monitoring program 700, for example. While FIG. 8 a shows astart and end of the local monitoring program 800 for the sake ofexplanation, in some examples the local monitoring program 800 maycontinuously execute, repeat, and/or loop.

In the example of FIG. 8 a , the local monitoring program 800 begins atblock 802. At block 802, the local monitoring program 800 receiveswelding data from one or more welding devices 399 in communication withthe local monitoring station 200. The welding data is further stored inthe local data repository 204. In some examples, the welding data maycomprise data pertaining to the operation of the welding device 399,such as, for example, arc count, deposition amount, current, voltage,wire feed speed, gas flow, torch work angle, torch travel angle, torchtip to work distance, torch travel speed, torch aim, arc length, and/orother appropriate data relating to operation of the welding device 399.In some examples, the welding device 399 may continuously orperiodically communicate the welding data to the local monitoringstation 200 while the welding device 399 is performing a weldingoperation. In some examples, the welding device 399 may communicate thewelding data to the local monitoring station 200 in response to arequest from the local monitoring station 200.

In the example of FIG. 8 a , the local monitoring program 800 proceedsto block 804 after block 802. At block 804, the local monitoring program800 handles event tracking operations, such as, for example, weldtracking and/or part tracking operations. For example, the localmonitoring program 800 may analyze the welding data received at block802 to detect certain events (e.g., workflow events, part trackingevents, trigger activation/deactivation events, arc start/stop events,etc.). For example, welding device 399 may communicate welding datadescribing data read by a sensor 150 that is indicative of a certainevent (e.g., wire spool change, loading of workpiece 110). In such anexample, the local monitoring station 200 may determine an event hasoccurred execute certain instructions (e.g., display schematics, issuealert, etc.) in view of that event. In some examples, the localmonitoring program 800 may store data representative of the detectedevents and/or instructions in the local data repository 204. In someexamples, the local monitoring program 800 may associate datarepresentative of the detected events and/or instructions with thewelding device 399 from which the welding data was received, and/or thejob session 450 with which the welding device 399 is associated, whenstoring in the local data repository 204.

In the example of FIG. 8 a , the local monitoring program 800 proceedsto block 806 after block 804. At block 806 the local monitoring program800 handles activity tracking operations. In some examples, the activitytracking at block 806 determines what current activity should berecorded and/or associated with a job session 450 and/or welding device399. The activity tracking operations of block 806 are explained furtherbelow with respect to FIG. 8 b.

In the example of FIG. 8 a , the local monitoring program 800 proceedsto block 808 after block 806. At block 808, the local monitoring program800 synchronizes the local data repository 204 with the central datarepository 400. In some examples, the synchronization at block 808 mayoccur in response to a synchronization request from the centralmonitoring station 302, an expiration of a threshold synchronizationtime period (e.g., stored in memory 210 and/or the local data repository204), and/or some other occurrence. After block 808, the localmonitoring program 800 ends.

FIG. 8 b is a flowchart illustrating an example implementation of theactivity tracking block 806 of the example local monitoring program 800of FIG. 8 a . As shown, the activity tracking block 806 begins at block810, where the local monitoring program 800 determines whether thecurrent activity should be recorded as an activity related to thewelding device 399. In some examples, this determination may comprisedetermining whether welding data has been recently (e.g., within somethreshold time period) received from a welding device 399 (e.g., awelding device 399 associated with an open job session 450). As shown,if welding data has been recently received, the local monitoring program800 proceeds to block 812, where the local monitoring program 800analyzes the welding data, determines a welding device related activitybased on the welding data, and sets the current activity to be thewelding device related activity. After block 812, the local monitoringprogram 800 ends. However, if the local monitoring program 800determines that the current activity is not a welding device relatedactivity at block 810, the local monitoring program 800 proceeds toblock 814.

At block 814, the local monitoring program 800 determines whether thelocal monitoring station 200 has received a user entered activity, suchas from the user device 350 (e.g., via SignalR), for example. If a userentered activity has not been received, the local monitoring program 800proceeds to block 820, which is further discussed below. If a userentered activity has been received, the local monitoring program 800proceeds to block 816, where the current activity is set to the userentered activity. After block 816, the local monitoring program 800proceeds to block 818, where the welding device 399 is enabled. Afterblock 818, the local monitoring program 800 ends.

In some examples, the welding device 399 may be enabled throughtransmission of a signal to from the local monitoring station 200 to thewelding device 399. For example, the signal may be indicative of arequest to enable the welding device 399. In some examples, the weldingdevice 399 may be a welding-type power supply 108 that has powerconversion circuitry 132 that only outputs welding-type power when anthe control circuitry 134 sends control signals to controllableswitching elements of the power conversion circuitry 132. In someexamples, the control circuitry 134 may be configured to cease sendingthe control signals to the controllable switching elements in responseto a disable signal received from the local monitoring station 200, andresume sending the control signals to the controllable switchingelements in response to an enable signal received from the localmonitoring station 200.

In some examples, the welding device 399 may be a welding-type powersupply 108, wire feeder 140, or gas supply 142 that only provides power,wire, and/or gas in response to a trigger signal received from thewelding torch 118. In such an example, the welding device 399 may beconfigured to ignore the trigger signal in response to a disable signalreceived from the local monitoring station 200, and/or stop ignoring thetrigger signal in response to an enable signal received form the localmonitoring station 200. In some examples, the welding device 399 may bea welding torch 118 that ceases to send the trigger signal in responseto a disable signal received from the local monitoring station 200, andresumes sending the trigger signal in response to an enable signalreceived form the local monitoring station 200.

In the example of FIG. 8 b , the local monitoring program 800 proceedsto block 820 if a user entered activity has not been received. At block820, the local monitoring program 800 determines whether a thresholdtime has passed since there has been a user entered activity (e.g.,block 814) or an automatically determined welding device 399 relatedactivity (e.g., block 810). In some examples, the threshold time periodmay be stored in memory 210 of the local monitoring station 200, sentfrom the central monitoring station 302, programmatically determined(e.g., by the processing circuitry 208 of the local monitoring station200), user entered, and/or otherwise provided. If the threshold time hasnot passed, the local monitoring program 800 ends. If the threshold timehas passed, the local monitoring program 800 determines there is somesort of downtime and proceeds to block 822.

In the example of FIG. 8 b , the local monitoring program 800 determineswhether the downtime is due to some known activity. In some examples,this determination may comprise determining whether there are any knownactivities (e.g., stored with the activity information 406) that overlapin time with the current date/time. For example, the activityinformation 406 may indicate that there is a scheduled break, shiftchange, maintenance, resupply, replacement, training, meeting, or otheractivity that is scheduled to occur at or near the current time. In someexamples, the determination may further comprise determining whether anyof the known activities that overlap in time are also associated with auser operating the welding device 399 and/or associated with the currentjob session 450. In some examples, the determination may compriseadditional, or alternative, considerations.

In the example of FIG. 8 b , if the local monitoring program 800determines that the downtime is due to a known activity at block 822,that known activity is set as the current activity at block 824, andassociated with a time period spanning the threshold time period ofblock 820 up to the current time at block 824. After block 824, thelocal monitoring program 800 ends. However, if the local monitoringprogram 800 determines that there is no known activity to which thedowntime may be attributed, the local monitoring program 800 and promptsthe user for some activity to which to attribute the downtime at block826. In some examples, a signal indicative of a prompt for the activityis sent to the user device 350 (e.g., via SignalR) and/or a prompt ispresented on the UI 202 of the local monitoring station 200. As shown,the local monitoring program 800 additionally disables the weldingdevice 399 at block 826, such that no further welding operations may beperformed using the welding device 399 until some activity isdetermined. This disabling may incentivize the user to provide anactivity to which the downtime may be attributed, which may furtherensure that the distributed weld monitoring system 300 receives all thenecessary information for monitoring. After block 826, the localmonitoring program 800 returns to block 810.

The distributed weld monitoring system 300 allows monitoring data to beinput via a user device 350 that may be more easily transported throughan expansive work environment than the local monitoring station 200.Additionally, by organizing the monitoring data according to jobs 420and job sessions 450 when collecting the monitoring data, it becomespossible to view and/or analyze the monitoring data according to eachjob and/or job session after the job is over, or even while the job isstill ongoing, which may assist in analysis. Because the distributedweld monitoring system works best when operators regularly providemonitoring input, in some examples, the distributed weld monitoringsystem 300 may also take steps to encourage operator input, such as by,for example, disabling one or more welding devices 399 that the operator116 is using until operator input is forthcoming.

The present method and/or system may be realized in hardware, software,or a combination of hardware and software. The present methods and/orsystems may be realized in a centralized fashion in at least onecomputing system, or in a distributed fashion where different elementsare spread across several interconnected computing or cloud systems. Anykind of computing system or other apparatus adapted for carrying out themethods described herein is suited. A typical combination of hardwareand software may be a general-purpose computing system with a program orother code that, when being loaded and executed, controls the computingsystem such that it carries out the methods described herein. Anothertypical implementation may comprise an application specific integratedcircuit or chip. Some implementations may comprise a non-transitorymachine-readable (e.g., computer readable) medium (e.g., FLASH drive,optical disk, magnetic storage disk, or the like) having stored thereonone or more lines of code executable by a machine, thereby causing themachine to perform processes as described herein.

While the present method and/or system has been described with referenceto certain implementations, it will be understood by those skilled inthe art that various changes may be made and equivalents may besubstituted without departing from the scope of the present methodand/or system. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the presentdisclosure without departing from its scope. Therefore, it is intendedthat the present method and/or system not be limited to the particularimplementations disclosed, but that the present method and/or systemwill include all implementations falling within the scope of theappended claims.

As used herein, “and/or” means any one or more of the items in the listjoined by “and/or”. As an example, “x and/or y” means any element of thethree-element set {(x), (y), (x, y)}. In other words, “x and/or y” means“one or both of x and y”. As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. In other words, “x, y and/or z” means “one or more of x, yand z”.

As utilized herein, the terms “e.g.,” and “for example” set off lists ofone or more non-limiting examples, instances, or illustrations.

As used herein, the terms “coupled,” “coupled to,” and “coupled with,”each mean a structural and/or electrical connection, whether attached,affixed, connected, joined, fastened, linked, and/or otherwise secured.As used herein, the term “attach” means to affix, couple, connect, join,fasten, link, and/or otherwise secure. As used herein, the term“connect” means to attach, affix, couple, join, fasten, link, and/orotherwise secure.

As used herein the terms “circuits” and “circuitry” refer to physicalelectronic components (i.e., hardware) and any software and/or firmware(“code”) which may configure the hardware, be executed by the hardware,and or otherwise be associated with the hardware. As used herein, forexample, a particular processor and memory may comprise a first“circuit” when executing a first one or more lines of code and maycomprise a second “circuit” when executing a second one or more lines ofcode. As utilized herein, circuitry is “operable” and/or “configured” toperform a function whenever the circuitry comprises the necessaryhardware and/or code (if any is necessary) to perform the function,regardless of whether performance of the function is disabled or enabled(e.g., by a user-configurable setting, factory trim, etc.).

As used herein, a control circuit may include digital and/or analogcircuitry, discrete and/or integrated circuitry, microprocessors, DSPs,etc., software, hardware and/or firmware, located on one or more boards,that form part or all of a controller, and/or are used to control awelding process, and/or a device such as a power source or wire feeder.

As used herein, the term “processor” means processing devices,apparatus, programs, circuits, components, systems, and subsystems,whether implemented in hardware, tangibly embodied software, or both,and whether or not it is programmable. The term “processor” as usedherein includes, but is not limited to, one or more computing devices,hardwired circuits, signal-modifying devices and systems, devices andmachines for controlling systems, central processing units, programmabledevices and systems, field-programmable gate arrays,application-specific integrated circuits, systems on a chip, systemscomprising discrete elements and/or circuits, state machines, virtualmachines, data processors, processing facilities, and combinations ofany of the foregoing. The processor may be, for example, any type ofgeneral purpose microprocessor or microcontroller, a digital signalprocessing (DSP) processor, an application-specific integrated circuit(ASIC), a graphic processing unit (GPU), a reduced instruction setcomputer (RISC) processor with an advanced RISC machine (ARM) core, etc.The processor may be coupled to, and/or integrated with a memory device.

As used, herein, the term “memory” and/or “memory device” means computerhardware or circuitry to store information for use by a processor and/orother digital device. The memory and/or memory device can be anysuitable type of computer memory or any other type of electronic storagemedium, such as, for example, read-only memory (ROM), random accessmemory (RAM), cache memory, compact disc read-only memory (CDROM),electro-optical memory, magneto-optical memory, programmable read-onlymemory (PROM), erasable programmable read-only memory (EPROM),electrically-erasable programmable read-only memory (EEPROM), acomputer-readable medium, or the like. Memory can include, for example,a non-transitory memory, a non-transitory processor readable medium, anon-transitory computer readable medium, non-volatile memory, dynamicRAM (DRAM), volatile memory, ferroelectric RAM (FRAM),first-in-first-out (FIFO) memory, last-in-first-out (LIFO) memory, stackmemory, non-volatile RAM (NVRAM), static RAM (SRAM), a cache, a buffer,a semiconductor memory, a magnetic memory, an optical memory, a flashmemory, a flash card, a compact flash card, memory cards, secure digitalmemory cards, a microcard, a minicard, an expansion card, a smart card,a memory stick, a multimedia card, a picture card, flash storage, asubscriber identity module (SIM) card, a hard drive (HDD), a solid statedrive (SSD), etc. The memory can be configured to store code,instructions, applications, software, firmware and/or data, and may beexternal, internal, or both with respect to the processor 130.

The term “power” is used throughout this specification for convenience,but also includes related measures such as energy, current, voltage, andenthalpy. For example, controlling “power” may involve controllingvoltage, current, energy, and/or enthalpy, and/or controlling based on“power” may involve controlling based on voltage, current, energy,and/or enthalpy.

As used herein, welding-type power refers to power suitable for welding,cladding, brazing, plasma cutting, induction heating, carbon arccutting, and/or hot wire welding/preheating (including laser welding andlaser cladding), carbon arc cutting or gouging, and/or resistivepreheating.

As used herein, a welding-type power supply and/or power source refersto any device capable of, when power is applied thereto, supplyingwelding, cladding, brazing, plasma cutting, induction heating, laser(including laser welding, laser hybrid, and laser cladding), carbon arccutting or gouging, and/or resistive preheating, including but notlimited to transformer-rectifiers, inverters, converters, resonant powersupplies, quasi-resonant power supplies, switch-mode power supplies,etc., as well as control circuitry and other ancillary circuitryassociated therewith.

Disabling of circuitry, actuators, and/or other hardware may be done viahardware, software (including firmware), or a combination of hardwareand software, and may include physical disconnection, de-energization,and/or a software control that restricts commands from being implementedto activate the circuitry, actuators, and/or other hardware. Similarly,enabling of circuitry, actuators, and/or other hardware may be done viahardware, software (including firmware), or a combination of hardwareand software, using the same mechanisms used for disabling.

What is claimed is:
 1. A welding system, comprising: a first localmonitoring station in communication with a first plurality of weldingdevices, the first local monitoring station being configured to receivefirst welding data from a first welding device of the first plurality ofwelding devices; a second local monitoring station in communication witha second plurality of welding devices, the second local monitoringstation being configured to receive second welding data from a secondwelding device of the second plurality of welding devices; a centralmonitoring station in communication with the first local monitoringstation and the second monitoring station, and configured to receive thefirst welding data from the first local monitoring station and receivethe second welding data from the second local monitoring station; and adata repository storing the first welding data and the second weldingdata received by the central monitoring station.
 2. The welding systemof claim 1, wherein at least one welding device of the first pluralityof welding devices or the second plurality of welding devices comprisesa welding-type power supply, a welding tool, a polishing tool, a sandingtool, an induction heating device, a gas supply, a wire feeder, or aclamp.
 3. The welding system of claim 1, wherein each welding device ofthe first plurality of welding devices or the second plurality ofwelding devices comprises a welding-type power supply, a welding tool, apolishing tool, a sanding tool, an induction heating device, a gassupply, a wire feeder, or a clamp.
 4. The welding system of claim 1,further comprising the first plurality of welding devices or the secondplurality of welding devices.
 5. The welding system of claim 1, whereinthe welding data comprises data pertaining to a number of welding arcs,an amount of deposited filler material, a welding current, a weldingvoltage, a welding wire feed speed, a gas flow rate, a torch work angle,a torch travel angle, a torch tip to work distance, a torch travelspeed, a torch aim, or an arc length.
 6. The welding system of claim 1,wherein the data repository further stores a data-device associationbetween the first or second welding data and a welding device identifierof the first or second welding device to which the first or secondwelding data pertains.
 7. The welding system of claim 6, wherein thedata repository further stores a data/device-session association betweenthe first or second welding data, or the welding device identifier, anda job session identifier of a welding job session.
 8. The welding systemof claim 7, wherein the data repository further stores asession-timestamp association between the job session identifier and oneor more job session timestamps representative of a time the welding jobsession occurred.
 9. The welding system of claim 8, wherein the datarepository further stores a session-activity association between the jobsession identifier and activity data pertaining to an activity thatoccurred during the time the welding job session occurred.
 10. Thewelding system of claim 9, wherein the data repository further stores auser-activity association between the activity data a user identifier ofa user who performed the activity.
 11. A welding system, comprising: adata repository configured to: store welding device data associated witha welding device identifier of a welding device to which the weldingdevice data pertains, store a data/device-session association betweenthe welding device data, or the welding device identifier, and a firstjob session identifier of a first welding job session, store asession-timestamp association between the first job session identifierand one or more job session timestamps representative of a time thefirst welding job session occurred, store a session-activity associationbetween the first job session identifier and activity data pertaining toan activity that occurred during the time the first welding job sessionoccurred, store a user-activity association between the activity dataand a user identifier of a user who performed the activity, store afirst job-session association between the first job session identifierand a job identifier of a welding job, store a second job-sessionassociation between a second job session and the job identifier of thewelding job, and store a job-timestamp association between the jobidentifier and one or more job timestamps representative of a timeperiod in which the welding job occurred, the job session havingoccurred during the time period in which the welding job occurred. 12.The welding system of claim 11, wherein neither the first job sessionidentifier nor the second job session identifier is associated with anyother job identifier of any other welding job.
 13. The welding system ofclaim 11, wherein the activity data comprises first activity datapertaining to a first activity and the session-activity associationcomprises a first session-activity association, the data repositorybeing further configured to store a second session-activity associationbetween the first job session identifier and second activity datapertaining to a second activity that occurred during the time the firstwelding job session occurred.
 14. The welding system of claim 13,wherein the data repository is further configured to: store a firstactivity-timestamp association between the first activity data and oneor more first activity timestamps representative of a first timeinterval when the first activity occurred, and store a secondactivity-timestamp association between the second activity data and oneor more second activity timestamps representative of a second timeinterval when the second activity occurred.
 15. The welding system ofclaim 11, wherein the job identifier is further associated with aplurality of user identifiers of users assigned to the welding job, theplurality of user identifiers comprising the user identifier.
 16. Thewelding system of claim 11, further comprising a central monitoringstation configured to: provide the welding data to the data repository,and receive the welding data from a local monitoring station.
 17. Thewelding system of claim 16, wherein the local monitoring station is incommunication with a plurality of welding devices, the plurality ofwelding devices comprising the welding device to which the welding datapertains.
 18. The welding system of claim 16, wherein the localmonitoring station comprises a first local monitoring station incommunication with a first plurality of welding devices, the weldingsystem further comprising a second local monitoring station incommunication with a second plurality of welding devices and the centralmonitoring station.
 19. The welding system of claim 11, wherein thewelding device comprises a welding-type power supply, a welding tool, apolishing tool, a sanding tool, an induction heating device, a gassupply, a wire feeder, or a clamp.
 20. The welding system of claim 11,wherein the welding data comprises data pertaining to a number ofwelding arcs, an amount of deposited filler material, a welding current,a welding voltage, a welding wire feed speed, a gas flow rate, a torchwork angle, a torch travel angle, a torch tip to work distance, a torchtravel speed, a torch aim, or an arc length.